slow-downers
So far \setcharacterstripping[1] is giving the right results. If the relevant
trackers are available, could add them to the attached test. But presumably you
know how and why it works even for a non-dimensionless glyph.
so you want to see soem zwj sumbol in a rendered text?
Onl
wiping. We can of course ignore in the
backend when zero width but then how to explain that they contributed to
the ht/dp (unless we wipe these dimensions) ... all slow-downers
so you want to see soem zwj sumbol in a rendered text?
Only in verbatim/\type'd text where it is appropriate, eve
so you want to see soem zwj sumbol in a rendered text?
Only in verbatim/\type'd text where it is appropriate, even necessary. Thanks
to Word/WYSIWYG, the rule is de facto, but it is not de jure -)
Ideally, Scintilla (Scite, Notepad++, etc.) should do the same, or provide a
toggle, as
r own visualization (consistent across fonts) and even then
it would add some mess because we're talking of a mix of characters that
can have gone (as part of rendering) or are not characters at all but
spacing
so, in that case only 'verbatim' is a candidate for visualization, not
so much typeset text
Hm
visualization (consistent across fonts) and even then
it would add some mess because we're talking of a mix of characters that
can have gone (as part of rendering) or are not characters at all but
spacing
so, in that case only 'verbatim' is a candidate for visualization, not
so much typeset te
in the font?
3. Ideally:
a. we want all Unicode control symbols to show up in verbatim or in \typebuffer
(as in a text editor);
b. we want all Unicode control symbols to be suppressed in final pdf output
(for, e.g., printing).
But some fonts meant for printing have symbols for Unicode control c
On 18/09/2023 17:07, Michael Loescher wrote:
\starttext
\type{hello}
\stoptext
here too (linux pop!os 22.04) something goes unexpected:
! Control sequence expected instead of undefined.
\buff_verbatim_type_normal
...chained \t!verbatim \currenttype \??type \clf_type
data
gt; tex error on line 2 in file Z:/test.tex: Control sequence
> expected instead of undefined
>
> \buff_verbatim_type_normal
> #1->\buff_verbatim_initialize_type_two \dostarttaggedchained \t!verbatim
> \currenttype \??type \clf_type data{\protecteddetokenize
> {#1}}tab{\
pe_two \dostarttaggedchained \t!verbatim
\currenttype \??type \clf_type data{\protecteddetokenize
{#1}}tab{\typeparameter \c!tab }method{\p_buff_option
}compact{\typeparameter \c!compact }escape{\typeparameter \c!escap
\type{hello}
1 \starttext
2 >> \type{hello}
3 \stoptext
Jeroen schrieb am 16.09.2023 um 22:28:
This MWE has a framed text for some verbatim text (code) with as title
ref. a counter 1, 2, etc.. Is there a way to change this frame text
title as following with the chapter number and a sequential number and
the title.
Code Fragment 1.1 (The First
ence={tit1}]
Some verbatim text
\stopCode
\startCode
[title={The Second Title},
reference={tit2}]
Some verbatim text
\stopCode
Refer to \in{code fragment}[tit1] bla
\stopchapter
\startchapter
[title=second]
\startCode
[title={The Third Title},
reference={tit3}]
Some verbatim text
> On 16 Sep 2023, at 21:28, Jeroen wrote:
>
> This MWE has a framed text for some verbatim text (code) with as title ref. a
> counter 1, 2, etc.. Is there a way to change this frame text title as
> following with the chapter number and a sequential number and th
This MWE has a framed text for some verbatim text (code) with as title ref.
a counter 1, 2, etc.. Is there a way to change this frame text title as
following with the chapter number and a sequential number and the title.
Code Fragment 1.1 (The First Title)
Code Fragment 1.2 (The Second Title
This is a longshot, but would be great to have. Below I have at MWE1 the
verbatim codefragment textbox I am using. I found in the forum MWE2 which
is a textbox with an automatic reference number. Is there a way to get the
same for MWE1 with automatic reference numbering like 1.1, 1.2 etc
Jeroen schrieb am 08.09.2023 um 13:09:
I am using the following to print some verbatim text in a frame. At
the right side, it keeps running out of the frame, is there a way to
prevent this with the MWE? This verbatim frame always is textwidth, is
there a way for a single frame just
I am using the following to print some verbatim text in a frame. At the
right side, it keeps running out of the frame, is there a way to prevent
this with the MWE? This verbatim frame always is textwidth, is there a way
for a single frame just for if the situation asks for it to have it only
have
s = {"hash",},
actions = function(h, a)
-- …
end, }
\stopluacode
But I didn’t find how to do environments.
When you just need an environment with a optional argument to pass user
values you can
use the userdata environment but be aware that you have some limitat
Dear Hans,
Thank you for your detailed answer. I'll wait then the next upload.
Kind regards
Marcus Vinicius
On Thu, Sep 7, 2023 at 2:36 PM Hans Hagen via ntg-context
wrote:
>
> On 9/7/2023 2:47 PM, Marcus Vinicius Mesquita wrote:
> > Dear List,
> >
> > The MWE below gives a pdf with two #'s
On 9/7/2023 2:47 PM, Marcus Vinicius Mesquita wrote:
Dear List,
The MWE below gives a pdf with two #'s instead of only one. Why is that?
\starttext
\startluacode
context.type("#")
\stopluacode
\stoptext
because by default tex loves to duplicate hashes when it serializes
token lists
Dear List,
The MWE below gives a pdf with two #'s instead of only one. Why is that?
\starttext
\startluacode
context.type("#")
\stopluacode
\stoptext
--
Todas as coisas fatigam o corpo, salvo a música, que não fatiga nem o
corpo nem seus membros, por ser descanso da alma, primavera do
of the
\everyinitializeverbatim register because it is used for
inline and display verbatim. A better place to add the option is
\buff_verbatim_initialize_typing_two for \starttyping
and \buff_verbatim_initialize_type_two for \type.
ok
Alex Leray schrieb am 17.08.2023 um 17:59:
Hi,
I think I need to use verbatim because I'm typesetting source code and
I need it to be as verbatim as possible.
For the moment, I'm manually inserting zero-width spaces... seems to
do the trick, although it's becoming unreadable :P
Which
Hi,
I think I need to use verbatim because I'm typesetting source code and I
need it to be as verbatim as possible.
For the moment, I'm manually inserting zero-width spaces... seems to do
the trick, although it's becoming unreadable :P
Thanks,
Alex
Le 17/08/23 à 17:22, Wolfgang Schuster
Alex Leray schrieb am 17.08.2023 um 14:41:
Hi,
I'd like to break lines in verbatim on certain characters like "/".
I can do it for normal texte, but not inside typing environment.
Do you need the verbatim environment or is the lines-environment sufficient.
\setuppa
, Alex Leray wrote:
Hi,
I'd like to break lines in verbatim on certain characters like "/".
I can do it for normal texte, but not inside typing environment.
Is there a way to achieve this?
For now do this:
\appendtoks
\usesetupsparameter\typingparameter
\to \everyinitiali
On 8/17/2023 2:41 PM, Alex Leray wrote:
Hi,
I'd like to break lines in verbatim on certain characters like "/".
I can do it for normal texte, but not inside typing environment.
Is there a way to achieve this?
For now do this:
\appendtoks
\usesetupsparameter\typin
Hi,
I'd like to break lines in verbatim on certain characters like "/".
I can do it for normal texte, but not inside typing environment.
Is there a way to achieve this?
Below is my test code.
Thanks,
Alex
* * *
\setuppapersize[A7]
\setbreakpoints[compound]
\starttext
1. This is
explain?
Hraban
Am 15.08.23 um 22:31 schrieb Hans Hagen via ntg-context:
Hi,
Especially for long verbatim lines we now can do this:
\starttext
\setupalign[hangright]
\starttyping
test test test test test test test test test test test test test test
test test test test test test test test
Hi,
Especially for long verbatim lines we now can do this:
\starttext
\setupalign[hangright]
\starttyping
test test test test test test test test test test test test test test
test test test test test test test test test test test test test
test test test test test test test test test test
nce
\strc_sectioning_initialize_increment ->\edef \currentheadincrement
verbatim is tricky because it changes the catcodes
here is a trick:
\definehead
[poem]
[section]
\setuphead
[poem]
[after=\startlines\tt, % after the head is placed
aftersection=\stoplines] % when we end this section
\startpoem
ipsum dolor sit amet consectetur.
\stoppoem
\stoptext
```
I get the following traceback:
```
tex error > tex error on line 6 in file
/home/ali/work/being_human/test.tex: ! Undefined control sequence
\strc_sectioning_initialize_increment ->\edef \currentheadincrement
verbatim is
dering; these
fillers in text are sort of special
Then again, the only way to resemble what TeX does is by re/defining
and copied verbatim from The TeXbook both rightarrowfill and
leftarrowfill
and hope for the best
and unlike with TeX in which an
\hbox to 1in{\vrule \rightarrowfill \ 1cm \lef
the \rightarrowfill or \leftarrowfill?
> >
> > I mean. Once you get the glues messed up, the whole box crumbles.
>
> I'm not sure how you can mess up glue so that the box is no longer a box.
> Boxes remain boxes.
I guess that's the same mentality behind a fixed glue in LMT
On Fri, 19 May 2023, Jeroen via ntg-context wrote:
> Many thanks. Is there a proper way to add some space (a couple of pt or em)
> to the left and the right of the text itself so the frame does not get so
> close to the text?
\framed[loffset=0.2ex, roffset=0.2ex]{...}
Also see:
chrieb am 19.05.2023 um 14:22:
> > In order to get some inline framed verbatim text, I have in the past
> > always used the following:
> >
> > \starttext
> >
> > This is an
> > \inframed
> > [frame=on,
> > corner=00,
> > radius=2mm,of
Jeroen via ntg-context schrieb am 19.05.2023 um 14:22:
In order to get some inline framed verbatim text, I have in the past
always used the following:
\starttext
This is an
\inframed
[frame=on,
corner=00,
radius=2mm,offset=-1.5pt]
{\ttx \bf example}
\stoptext
Since this has come-up
In order to get some inline framed verbatim text, I have in the past always
used the following:
\starttext
This is an
\inframed
[frame=on,
corner=00,
radius=2mm,offset=-1.5pt]
{\ttx \bf example}
\stoptext
Since this has come-up more and more often, I created the following:
\define[1
On 2/4/23 07:49, Hugo Landau via ntg-context wrote:
> On this page of the wiki there is an example for wrapping long words,
> like long hexadecimal strings:
>
> https://wiki.contextgarden.net/Wrapping
>
> This example is buggy because it deletes one character at the point that
> it is wrapped.
On 2/5/2023 4:52 PM, Pablo Rodriguez via ntg-context wrote:
On 2/5/23 13:13, Hans Hagen via ntg-context wrote:
On 2/5/2023 12:32 PM, Pablo Rodriguez via ntg-context wrote:
[...]
Are we missing something or is this a bug?
what do you expect as result? (maybe try \righthyphenmin=1)
Line
On 2/5/23 13:13, Hans Hagen via ntg-context wrote:
> On 2/5/2023 12:32 PM, Pablo Rodriguez via ntg-context wrote:
>> [...]
>> Are we missing something or is this a bug?
> what do you expect as result? (maybe try \righthyphenmin=1)
Line breaks are removing characters.
In the sample below, output
On 2/5/2023 12:32 PM, Pablo Rodriguez via ntg-context wrote:
On 2/4/23 10:37, Pablo Rodriguez via ntg-context wrote:
On 2/4/23 07:49, Hugo Landau via ntg-context wrote:
On this page of the wiki there is an example for wrapping long words,
like long hexadecimal strings:
On 05/02/2023 12:32, Pablo Rodriguez via ntg-context wrote:
Are we missing something or is this a bug?
If you add a \tt at the beginning, the lines have different length.
not sure why, but there is a reason to it...
\startTEXpage[offset=3em]
\tt
\setupalign[tolerant,stretch]
\dorecurse
On 2/4/23 10:37, Pablo Rodriguez via ntg-context wrote:
> On 2/4/23 07:49, Hugo Landau via ntg-context wrote:
>> On this page of the wiki there is an example for wrapping long words,
>> like long hexadecimal strings:
>>
>> https://wiki.contextgarden.net/Wrapping
>>
>> This example is buggy because
On 2/4/23 07:49, Hugo Landau via ntg-context wrote:
> On this page of the wiki there is an example for wrapping long words,
> like long hexadecimal strings:
>
> https://wiki.contextgarden.net/Wrapping
>
> This example is buggy because it deletes one character at the point that
> it is wrapped.
>
On this page of the wiki there is an example for wrapping long words,
like long hexadecimal strings:
https://wiki.contextgarden.net/Wrapping
This example is buggy because it deletes one character at the point that
it is wrapped.
In the example given, running context turns '257a410' into
Am Sat, 28 Jan 2023 03:01:24 +0100 schrieb Kalouguine Andre via
ntg-context:
> I'm trying to make a verbatim block of text with copiable leading spaces
> so that students can just copy my Python code snippets into their IDE.
This basically doesn't work (quite unrelated to the tex code).
T
On 1/29/23 17:58, Kalouguine Andre via ntg-context wrote:
> On 28.01.2023 22:54, Hans Hagen via ntg-context wrote:
>> […]
>> so: this is all very viewer dependent! (The suggested comment method
>> is more reliable.)
>
> Unfortunately as I just found out, comments are also viewer dependent...
>
Acrobat). Right you are, it works with
> your method, thanks!
> I think the students have Evince so perhaps it's the best solution in the
> absence
there are some provisions for spaces in text but for verbatim it is a
bit more tricky
\setuptyping[space=on]
you now see visual spaces show up tha
solution in
the absence
there are some provisions for spaces in text but for verbatim it is a
bit more tricky
\setuptyping[space=on]
you now see visual spaces show up that can be copied
now, say that we add real spaces, which you can do after and this (in
cont-new.mkxl):
\unprotect
ence
of copiable spaces in verbatim mode.
Thanks again!
Best regards,
Andre___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mail
On 1/28/23 14:31, Kalouguine Andre via ntg-context wrote:
> Hi Pablo,
Hi André,
> [...]
> That's actually something I had never thought of, using PDF comments,
> thanks!.
When I faced a similar task, I thought it could be the way of solving
the issue (how to copy and paste ConTeXt code and
Hi Pablo,
> \showframe
> \setupinteraction[state=start]
> \starttext
> \startbuffer[abc]
> def foo(x):
> if x == 0:
> bar()
> else:
> baz(x)
> foo(x - 1)
> \stopbuffer
> \comment[location=leftmargin,
> space=yes,
> buffer=abc,
> title={Python code}]
> {}\typebuffer[abc]
> \stoptext
>
> This
On 1/28/23 03:01, Kalouguine Andre via ntg-context wrote:
> Good day to everyone,
>
> I'm trying to make a verbatim block of text with copiable leading spaces
> so that students can just copy my Python code snippets into their IDE.
Hi André,
I wonder whether I’m gettin
Good day to everyone,
I'm trying to make a verbatim block of text with copiable leading spaces
so that students can just copy my Python code snippets into their IDE. I
believe the question has been asked before (though I confess I can't
find the right search terms to find the answer again). I
However, whatever I try, I get the serialized xml typeset, with all
verbatim, instead of processed. Here's what I've tried:
\startxmlsetups xml:chapter:example
\xmlfirst {#1} {.} \par
\stopxmlsetups
lxml.command (current_example, ".", "xml:chapter:example")
or
xml.spr
to text, which means that it is no longer possible
to "flush" the XML for further processing as XML. The result is that any
unresolved XML tags are written verbatim to the PDF:
https://i.stack.imgur.com/9ZFND.png
There are two other issues with this approach. First is efficien
flush" the XML for further processing as XML. The result is that any
unresolved XML tags are written verbatim to the PDF:
https://i.stack.imgur.com/9ZFND.png
There are two other issues with this approach. First is efficiency. Second
is that the processing function would have to be called for
On Fri, 12 Aug 2022 at 23:20, Aditya Mahajan wrote:
> On Fri, 12 Aug 2022, Mojca Miklavec via ntg-context wrote:
>
> > (a) I don't know how to turn program listing (verbatim code) from xml
> > to (perhaps, vim-based) syntax highlighting (but most importantly, to
> > make su
issues:
> >
> > (a) I don't know how to turn program listing (verbatim code) from xml
> > to (perhaps, vim-based) syntax highlighting (but most importantly, to
> > make sure that line breaks work properly)
>
> Does something like this work:
>
> https://wiki.con
> Hi,
>
> Hans helped me out with some asciidoc processing a while ago.
>
> I played a bit further, but I'm currently facing two minor issues:
>
> (a) I don't know how to turn program listing (verbatim code) from xml
> to (perhaps, vim-based) syntax highlighting (but mos
On Fri, 12 Aug 2022, Mojca Miklavec via ntg-context wrote:
> Hi,
>
> Hans helped me out with some asciidoc processing a while ago.
>
> I played a bit further, but I'm currently facing two minor issues:
>
> (a) I don't know how to turn program listing (verbatim code) from x
Hi,
Hans helped me out with some asciidoc processing a while ago.
I played a bit further, but I'm currently facing two minor issues:
(a) I don't know how to turn program listing (verbatim code) from xml
to (perhaps, vim-based) syntax highlighting (but most importantly, to
make sure that line
with this (context speak):
\def\textbf#1{\type{}#1\type{}}
so, you define all the commands that you use (normally a subset of what
a macro package provides, you just ignore what doesn't make sense)
then you define a very large page (say A1) that you use completely
then you typeset the document in verbatim
Hans Hagen via ntg-context schrieb am 31.07.2021 um 00:18:
On 7/30/2021 9:12 PM, Jeroen via ntg-context wrote:
I am using the following preamble to put a frame around
verbatim text. How can I have all the text start some 5pt from the
frame and how can I get rounded corners, corner=0 does
On 7/30/2021 9:12 PM, Jeroen via ntg-context wrote:
I am using the following preamble to put a frame around verbatim text.
How can I have all the text start some 5pt from the frame and how can I
get rounded corners, corner=0 does not seem to work
\setupcolors[state=start]
\setupcolor[xwi
I am using the following preamble to put a frame around verbatim text. How
can I have all the text start some 5pt from the frame and how can I get
rounded corners, corner=0 does not seem to work
\setupcolors[state=start]
\setupcolor[xwi]
\definetextbackground
[Code]
[frame
- is typeset as
> > > > an en-dash in LMTX (but not in MKIV, as documented). Could you look into
> > > > that?
> > >
> > > best is that the module uses:
> > >
> > > \the\everyinitializeverbatim
> > >
> > > because there we
is that the module uses:
\the\everyinitializeverbatim
because there we disable all kind of non verbatim stuff
Thanks. It took a few trial and error that \the\everyinitializeverbatim must
come after \usealignparameter. However, using \nohypencollapsing after
\usealignparameter means that I cannot get
est is that the module uses:
>
> \the\everyinitializeverbatim
>
> because there we disable all kind of non verbatim stuff
Thanks. It took a few trial and error that \the\everyinitializeverbatim must
come after \usealignparameter. However, using \nohypencollapsing after
\usealignparameter means that
look into
that?
best is that the module uses:
\the\everyinitializeverbatim
because there we disable all kind of non verbatim stuff
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat
On 4/26/2021 12:23 PM, Floris van Manen wrote:
\starttext
\starttyping[escape=@]
1 137 26 25 > 1 69 32
2 @btex@bgroup@red@bf 137 @egroup@etex 26 25 > 1 69 32
3 @btex@bgroup@red@bf 137 @egroup@etex 26 25 > 1 69 32
4 137 26 25 > 1 69 32
5
Aparently all spaces after @etex get reduced to one only.
I'd expect that to happen inside @btex and @etex
\starttext
\starttyping[escape=@]
1 137 26 25 >1 69 32
2 @btex@bgroup@red@bf 137 @egroup@etex 26 25 >1 69 32
3 @btex@bgroup@red@bf 137 @egroup@etex 26 25
On 26/04/2021 10:59, Hans Hagen wrote:
\starttext
\starttyping[escape=/]
one two three
four /btex/bgroup/red five /egroup/etex six
seven eight nine
\stoptyping
\stoptext
That works indeed! Thanks.
Are there restriction on what context commands can be given inside the
bgroup? e.g. I tried
On 4/26/2021 10:25 AM, Floris van Manen wrote:
What is the easiest way, if possible, to highlight some sections of
verbatim text?
given:
\starttyping
one two three
four five six
seven eight nine
\stoptyping
i'd like to color the word 'five' in red, or italic.
\starttext
\starttyping[escape
What is the easiest way, if possible, to highlight some sections of
verbatim text?
given:
\starttyping
one two three
four five six
seven eight nine
\stoptyping
i'd like to color the word 'five' in red, or italic.
.Floris
spaces
and empty lines often matter
if you use the scite lexer (in verbatim) you also get an idea how I see
the source
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061
in the
process of enhancing that, this traditional -- and --- replacement now
kicks in before hyphenation.
It can be disabled by \nohyphencollapsing, which actually happens in for
instance verbatim and it can be applied locally if needed. There might
be places where you expect this to happen so let
On 12/3/2020 12:04 PM, Stephen Gaito wrote:
- very large (1,000+ pages),
not that large, literate code is often verbatim so that doesn't take
much runtime either
- highly cross-referenced documents,
ok, that demands runs
- with embedded literate-programmed code (which needs
orecurse, such that \dorecurse{10}{\type{ab c}}
> > does not squash the spaces?
>
> Verbatim in arguments of other commands is tricky because in case with
> \dorecurse the loop reads the content before it is passed to type, as a
> result of this process all spaces are collapsed.
Sylvain Hubert schrieb am 08.11.2020 um 17:56:
Hi Wolfgang,
I'm sorry that the question was not clear enough. Let me ask in this way:
how to define a \dorecurse, such that \dorecurse{10}{\type{a b c}}
does not squash the spaces?
Verbatim in arguments of other commands is tricky because
arttext
> > \startLUA
> > whatever
> > \stopLUA
> > \stoptext
> >
> > In contrast to ConTeXt MKIV, the leading four spaces in front of
> > "whatever" are not removed when processing the verbatim text:
> >
> > MKIV output:
>
processing the verbatim text:
MKIV output:
whatever
LMTX output:
whatever
Is there a way to get the old MKIV behavior back?
\setuptyping[LUA][strip=yes]
Wolfgang
___
If your question is of interest to othe
Dear List,
I am using ConTeXt LMTX 2018.05.19 21:46. Consider the following MWE:
\starttext
\startLUA
whatever
\stopLUA
\stoptext
In contrast to ConTeXt MKIV, the leading four spaces in front of "whatever"
are not removed when processing the verbatim text:
MKIV output:
what
On Tue, Sep 1, 2020 at 10:50 AM Christoph Reller
wrote:
> I am using ConTeXt LMTX 2020.08.28 13:58 with the following M(N)WE:
>
> \definetype[typeLUA][option=LUA]
> \setbreakpoints[compound]
> \starttext
> \typeLUA{function(argument)}
> \stoptext
>
> Sadly, it does not compile.
>
I found that
Dear List,
I am using ConTeXt LMTX 2020.08.28 13:58 with the following M(N)WE:
\definetype[typeLUA][option=LUA]
\setbreakpoints[compound]
\starttext
\typeLUA{function(argument)}
\stoptext
Sadly, it does not compile. The problem seems to be the simultaneous use of
compound breakpoints and
ups or ignores macros AND prints braces "{"
> > and "}" as if it were in verbatim mode depending on the content being
> > on the document or loaded via Lua, even when context.escape is used.
> > How to keep {\it braced content}? Thank you in advance.
>
> Are you trying to types
Jairo A. del Rio schrieb am 08.08.2020 um 16:31:
Thank you very much! Something else happens:
\applytosplitstringwordspaced\somemacro{Content and {\tt typewriter}
more content}
either ignores braced groups or ignores macros AND prints braces "{"
and "}" as if it w
Thank you very much! Something else happens:
\applytosplitstringwordspaced\somemacro{Content and {\tt typewriter} more
content}
either ignores braced groups or ignores macros AND prints braces "{" and
"}" as if it were in verbatim mode depending on the content being on the
do
0%
tables 1033231%
verbatim 221777%
whitespace 1073028%
xml 155 9 6%
6293 236638%
___
If your question is of interest to othe
iple output for
> publishing
> ane educational purposes. And it looks pretty good too.
>
Thank you very much i will do. You are refering to Thomas Schmitz?
\setupbackend[
export=yes,
xhtml=yes
]
\setupexport[
title={linenumber placement missmatch example in export},
subtitle={},
au
attributes the corresponding tags
should receive.
Second i noticed that even in verbatim the line numbers are not on the
line they number but are, due to late injections printed on an empty
line in xhtml. Needs improvement here too.
All the above and some more forces me to push my plans to publish my
ding tags
> should receive.
>
> Second i noticed that even in verbatim the line numbers are not on the
> line they number but are, due to late injections printed on an empty
> line in xhtml. Needs improvement here too.
>
>
> All the above and some more forces me to p
end exporter.
Please increase the USB of ConTeXt by improoving the xml/xhtml exporter
backend by allowing modules to hook into it, defining how the contotent
should be processed and what css attributes the corresponding tags
should receive.
Second i noticed that even in verbatim the line numbers a
Subject: [NTG-context] Source Code with Bolded Keywords
> Message-ID:
> j5f28-8qv3ykrp+ev+ukrf0q+sp3mabskapxbkvn956...@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hello,
>
> I am trying to typeset source code for a custom progr
Yves Cloutier schrieb am 14.03.2020 um 16:54:
Hello,
I am trying to typeset source code for a custom programming language and
would like to have the keywords in bold text.
I tried following the example found here regarding verbatim displays:
https://www.contextgarden.net/Verbatim_text
Hello,
I am trying to typeset source code for a custom programming language and
would like to have the keywords in bold text.
I tried following the example found here regarding verbatim displays:
https://www.contextgarden.net/Verbatim_text#Displayed_text
Specifically the C example, however
On 8/28/2019 8:14 PM, Fabrice L wrote:
Dear list,
I’m using colored verbatim code (for course notes). In the past, I
modified verb-mp.mkii for the langage I need (SAS). This code works fine
with MKII:
%——
\setupcolors[state=start]
\definetyping [MP] [option=MP]
\starttext
A example
Dear list,
I’m using colored verbatim code (for course notes). In the past, I modified
verb-mp.mkii for the langage I need (SAS). This code works fine with MKII:
%——
\setupcolors[state=start]
\definetyping [MP] [option=MP]
\starttext
A example:
\startMP
draw (0,0) withpen pencircle 1in
tion
>> passing between lua and ConTeXt has me confused and tangled in a knot.
>> Below is a minimal almost-working example. The issue is in the line
>> {\ctxlua{userdata.addTempToBuffer('#1', [==[\getnumber[problem]]==])}}
>> which ends up putting the verbatim
ng to work. The delayed evaluation and information
passing between lua and ConTeXt has me confused and tangled in a knot.
Below is a minimal almost-working example. The issue is in the line
{\ctxlua{userdata.addTempToBuffer('#1', [==[\getnumber[problem]]==])}}
which ends up putting the verba
1 - 100 of 767 matches
Mail list logo
